Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc4e7cf0428b7017d3bc3480221daa85f9eeed60fb13bd3e8e109aad3f9948e5

Tx prefix hash: b42ec52acecc05ad86484511bfe657da88080c5bc27a398c54ade01518de9775
Tx public key: 7677850227825f2b0904e4ca951c4bf6fc5b6e7e5d1ea039819cac4fd8fbae06
Timestamp: 1733940560 Timestamp [UCT]: 2024-12-11 18:09:20 Age [y:d:h:m:s]: 00:097:16:32:39
Block: 1173042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69606 RingCT/type: yes/0
Extra: 017677850227825f2b0904e4ca951c4bf6fc5b6e7e5d1ea039819cac4fd8fbae06021100000002c7ca14c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bd73f50d36e33eb905af4d9f8327a4c63fbb21b1a1a62029464bf740a258974 0.600000000000 1659015 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": 1173052, "vin": [ { "gen": { "height": 1173042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bd73f50d36e33eb905af4d9f8327a4c63fbb21b1a1a62029464bf740a258974" } } ], "extra": [ 1, 118, 119, 133, 2, 39, 130, 95, 43, 9, 4, 228, 202, 149, 28, 75, 246, 252, 91, 110, 126, 93, 30, 160, 57, 129, 156, 172, 79, 216, 251, 174, 6, 2, 17, 0, 0, 0, 2, 199, 202, 20, 193, 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