Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fd4ecc9426a59257bb456c187ea15c292f209a7056c57fc8288a89ab2f82ac4

Tx prefix hash: 29d9ed71b8f0ffd361635069a4c8251dc7cf2ce6a25411a4b33169ef04a2f0fc
Tx public key: 29f393097b77160315f1135cbbb2e644bf7fb3f50560b13aa36604a01b59e4ab
Timestamp: 1711532063 Timestamp [UCT]: 2024-03-27 09:34:23 Age [y:d:h:m:s]: 01:046:11:06:36
Block: 987376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294174 RingCT/type: yes/0
Extra: 0129f393097b77160315f1135cbbb2e644bf7fb3f50560b13aa36604a01b59e4ab0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 756fa9d853517e2118d56d626cdeae3b6dd39ba0b45354a02d2ba085275bf9ea 0.600000000000 1447625 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": 987386, "vin": [ { "gen": { "height": 987376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "756fa9d853517e2118d56d626cdeae3b6dd39ba0b45354a02d2ba085275bf9ea" } } ], "extra": [ 1, 41, 243, 147, 9, 123, 119, 22, 3, 21, 241, 19, 92, 187, 178, 230, 68, 191, 127, 179, 245, 5, 96, 177, 58, 163, 102, 4, 160, 27, 89, 228, 171, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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