Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5bb48a05ef6a4c29d08c077026846caa2a57042632fe9e560b8593917052265

Tx prefix hash: e7e4137839f61ef4d29c3a3f97453a3d2672e0029f2c865c911bf040bb1c8a2c
Tx public key: d9d6500fb1a5e8e50d1dd7a4ba06b8b8779355ef30c6b67835e4329999db7d6c
Timestamp: 1635056113 Timestamp [UCT]: 2021-10-24 06:15:13 Age [y:d:h:m:s]: 04:024:06:13:33
Block: 359321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1054051 RingCT/type: yes/0
Extra: 01d9d6500fb1a5e8e50d1dd7a4ba06b8b8779355ef30c6b67835e4329999db7d6c0211000000067e786c8c000000000000000000

1 output(s) for total of 39.574986528000 dcy

stealth address amount amount idx
00: b61482327929fdc49adb098dde053a77b909f19d48b93e5ecab45820b5f8d73e 39.574986528000 731764 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": 359331, "vin": [ { "gen": { "height": 359321 } } ], "vout": [ { "amount": 39574986528, "target": { "key": "b61482327929fdc49adb098dde053a77b909f19d48b93e5ecab45820b5f8d73e" } } ], "extra": [ 1, 217, 214, 80, 15, 177, 165, 232, 229, 13, 29, 215, 164, 186, 6, 184, 184, 119, 147, 85, 239, 48, 198, 182, 120, 53, 228, 50, 153, 153, 219, 125, 108, 2, 17, 0, 0, 0, 6, 126, 120, 108, 140, 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