Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 333fe69db8699ee7f1524035b90db2acbf00d8c9672209862c029d53cafc400c

Tx prefix hash: b81dbff2fea7bad2bf989fb3eba55e7e30a752ceb29d4137722b952e7df85e7f
Tx public key: e44e8d9217c404a1b007ceff4cc011dcb0f107d0ad1b98cc1310ced70325948e
Timestamp: 1699969517 Timestamp [UCT]: 2023-11-14 13:45:17 Age [y:d:h:m:s]: 01:141:12:22:40
Block: 891494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362313 RingCT/type: yes/0
Extra: 01e44e8d9217c404a1b007ceff4cc011dcb0f107d0ad1b98cc1310ced70325948e02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.682512009000 dcy

stealth address amount amount idx
00: 2efa8c658f406285196edb08ba21060b2724126ec3e98c6268cb0dc2f0962fe5 0.682512009000 1347545 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": 891504, "vin": [ { "gen": { "height": 891494 } } ], "vout": [ { "amount": 682512009, "target": { "key": "2efa8c658f406285196edb08ba21060b2724126ec3e98c6268cb0dc2f0962fe5" } } ], "extra": [ 1, 228, 78, 141, 146, 23, 196, 4, 161, 176, 7, 206, 255, 76, 192, 17, 220, 176, 241, 7, 208, 173, 27, 152, 204, 19, 16, 206, 215, 3, 37, 148, 142, 2, 17, 0, 0, 0, 2, 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