Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fddf5e2dbaac1f40a21662c5a559f3f52b1d4d15b7bf26aa1d6421e12992a458

Tx prefix hash: 44ce77999ec2699aca8f275b9a75b5a356945196cbb63eb3371e40a6580d05c1
Tx public key: eae1daecdffabda8547d9e9f0c7c456d58e30e0a775291d5bd6242ec214197f7
Timestamp: 1731773696 Timestamp [UCT]: 2024-11-16 16:14:56 Age [y:d:h:m:s]: 00:157:09:39:19
Block: 1155062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112330 RingCT/type: yes/0
Extra: 01eae1daecdffabda8547d9e9f0c7c456d58e30e0a775291d5bd6242ec214197f702110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc5003c59407855892d32bf0e5553865eb59346235c8925820ec9b2cbbad2dbb 0.600000000000 1640675 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": 1155072, "vin": [ { "gen": { "height": 1155062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc5003c59407855892d32bf0e5553865eb59346235c8925820ec9b2cbbad2dbb" } } ], "extra": [ 1, 234, 225, 218, 236, 223, 250, 189, 168, 84, 125, 158, 159, 12, 124, 69, 109, 88, 227, 14, 10, 119, 82, 145, 213, 189, 98, 66, 236, 33, 65, 151, 247, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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