Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27dd4d144131104b24506b8919f488aa82d532b346ed9044156b23da8289eef6

Tx prefix hash: 152e8e052f6cc945ae9aa8e738fc564739cfde18df007349c774f87d5fdc8ed3
Tx public key: 0406b20126c870d7dd0af8d2dcd4a91d17feae2714d9e74681b719fba307b135
Timestamp: 1701956161 Timestamp [UCT]: 2023-12-07 13:36:01 Age [y:d:h:m:s]: 01:353:10:58:34
Block: 907967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511495 RingCT/type: yes/0
Extra: 010406b20126c870d7dd0af8d2dcd4a91d17feae2714d9e74681b719fba307b13502110000000d33af99f4000000000000000000

1 output(s) for total of 0.601905603000 dcy

stealth address amount amount idx
00: e996e5b6f8d86ec2dabc44034179652e71bae9e2c86ca2202c8393ff9ba8e19a 0.601905603000 1364968 of 0

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": 907977, "vin": [ { "gen": { "height": 907967 } } ], "vout": [ { "amount": 601905603, "target": { "key": "e996e5b6f8d86ec2dabc44034179652e71bae9e2c86ca2202c8393ff9ba8e19a" } } ], "extra": [ 1, 4, 6, 178, 1, 38, 200, 112, 215, 221, 10, 248, 210, 220, 212, 169, 29, 23, 254, 174, 39, 20, 217, 231, 70, 129, 183, 25, 251, 163, 7, 177, 53, 2, 17, 0, 0, 0, 13, 51, 175, 153, 244, 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