Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b1d3597257cf2ea182ee80455f69fd035cf511ad9df554fcc9086b4e28239ea

Tx prefix hash: ee8de828218b914343d1fc3c06d0106a4db3fe69146f005a928d1fb98859649c
Tx public key: b1fac6d83893d8c20d0833be1e9900a652cc2677e50c9cdb2ecfab75a641b191
Timestamp: 1673975120 Timestamp [UCT]: 2023-01-17 17:05:20 Age [y:d:h:m:s]: 02:075:10:04:47
Block: 676848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 575557 RingCT/type: yes/0
Extra: 01b1fac6d83893d8c20d0833be1e9900a652cc2677e50c9cdb2ecfab75a641b19102110000000175e3f0e9000000000000000000

1 output(s) for total of 3.510116657000 dcy

stealth address amount amount idx
00: 6d311134f7476664d3355d7511585373c54a9ef847c0d1187cb7b1ddd3bf7340 3.510116657000 1118603 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": 676858, "vin": [ { "gen": { "height": 676848 } } ], "vout": [ { "amount": 3510116657, "target": { "key": "6d311134f7476664d3355d7511585373c54a9ef847c0d1187cb7b1ddd3bf7340" } } ], "extra": [ 1, 177, 250, 198, 216, 56, 147, 216, 194, 13, 8, 51, 190, 30, 153, 0, 166, 82, 204, 38, 119, 229, 12, 156, 219, 46, 207, 171, 117, 166, 65, 177, 145, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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