Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70aaf1b74255f897db83b7865bc76df1de479a38b0db1ddd11fd4b0f74151296

Tx prefix hash: 95bb348255719a92cde910b35c9a7cd04b4c72e84b2506cfb9755186b605bb7d
Tx public key: d81e3b40e9e5c8a284b7d0b984bcebc262cb1b4d501fdfd426e81e531640f09d
Timestamp: 1702873626 Timestamp [UCT]: 2023-12-18 04:27:06 Age [y:d:h:m:s]: 01:121:21:40:51
Block: 915565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348255 RingCT/type: yes/0
Extra: 01d81e3b40e9e5c8a284b7d0b984bcebc262cb1b4d501fdfd426e81e531640f09d02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2f2987c67037b05fbc57a83d7089ea8ebc809b88558192444f566b068e30493 0.600000000000 1372961 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": 915575, "vin": [ { "gen": { "height": 915565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2f2987c67037b05fbc57a83d7089ea8ebc809b88558192444f566b068e30493" } } ], "extra": [ 1, 216, 30, 59, 64, 233, 229, 200, 162, 132, 183, 208, 185, 132, 188, 235, 194, 98, 203, 27, 77, 80, 31, 223, 212, 38, 232, 30, 83, 22, 64, 240, 157, 2, 17, 0, 0, 0, 5, 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