Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c44f5dce69cb9544c3fc0571ffb8de6a93408fe666c0a7bd6669d06bccfef01

Tx prefix hash: 621c897ac3710bcfa761ebe8d88a902589a19670c805cd50751a8d13c02d0eef
Tx public key: f539063ee0a0af5ed0f2c84c0223bffb93bc15372d267d32e469a5ca8af4307f
Timestamp: 1712368084 Timestamp [UCT]: 2024-04-06 01:48:04 Age [y:d:h:m:s]: 00:363:23:05:37
Block: 994252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260241 RingCT/type: yes/0
Extra: 01f539063ee0a0af5ed0f2c84c0223bffb93bc15372d267d32e469a5ca8af4307f02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd3c08ad693360cd6e0a61c0354ac9d1f04032d59563454c01c946ac7a0b2b29 0.600000000000 1454654 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": 994262, "vin": [ { "gen": { "height": 994252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd3c08ad693360cd6e0a61c0354ac9d1f04032d59563454c01c946ac7a0b2b29" } } ], "extra": [ 1, 245, 57, 6, 62, 224, 160, 175, 94, 208, 242, 200, 76, 2, 35, 191, 251, 147, 188, 21, 55, 45, 38, 125, 50, 228, 105, 165, 202, 138, 244, 48, 127, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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