Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 57bbaeeaa3ec238734b5b52339e319bc3ab7a8c89bce13caa503a13375e6b23f

Tx prefix hash: 593bf8a2936a7db5f3d651c1464c32582124a8df26708e53640209fcf4ab0a40
Tx public key: 12d753238bf7b04873def94d1ab60dfeddf219a4b95d6d2a2c768b6ef294d14f
Timestamp: 1743848897 Timestamp [UCT]: 2025-04-05 10:28:17 Age [y:d:h:m:s]: 00:228:17:05:20
Block: 1254779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161196 RingCT/type: yes/0
Extra: 0112d753238bf7b04873def94d1ab60dfeddf219a4b95d6d2a2c768b6ef294d14f021100000003a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b13ccad9bc520af91232125db3cf9f635a38baf53a76a599aa481067f6158056 0.600000000000 1741860 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1254789, "vin": [ { "gen": { "height": 1254779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b13ccad9bc520af91232125db3cf9f635a38baf53a76a599aa481067f6158056" } } ], "extra": [ 1, 18, 215, 83, 35, 139, 247, 176, 72, 115, 222, 249, 77, 26, 182, 13, 254, 221, 242, 25, 164, 185, 93, 109, 42, 44, 118, 139, 110, 242, 148, 209, 79, 2, 17, 0, 0, 0, 3, 162, 237, 1, 107, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8