Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86e07c061647c72dfad3dd2c83c78da7b39a53569c6f45e79016e490c95497d1

Tx prefix hash: fcd3fe9f16cb1889efe4c98b779605b7bc8821c1b7c9bb4492f7b16ba05f756a
Tx public key: 0ac8da7a541d77b41796f7e7c54b9124b1c8432dea76178d1f7dfc8ce50b2429
Timestamp: 1659389807 Timestamp [UCT]: 2022-08-01 21:36:47 Age [y:d:h:m:s]: 02:106:01:01:14
Block: 556649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597184 RingCT/type: yes/0
Extra: 010ac8da7a541d77b41796f7e7c54b9124b1c8432dea76178d1f7dfc8ce50b2429021100000001aac913b7000000000000000000

1 output(s) for total of 8.781948977000 dcy

stealth address amount amount idx
00: f2e12d44802879410ceb7fa04fbf9b2f4aea706d8d48170ad3b9ae3305dfc3b4 8.781948977000 988595 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": 556659, "vin": [ { "gen": { "height": 556649 } } ], "vout": [ { "amount": 8781948977, "target": { "key": "f2e12d44802879410ceb7fa04fbf9b2f4aea706d8d48170ad3b9ae3305dfc3b4" } } ], "extra": [ 1, 10, 200, 218, 122, 84, 29, 119, 180, 23, 150, 247, 231, 197, 75, 145, 36, 177, 200, 67, 45, 234, 118, 23, 141, 31, 125, 252, 140, 229, 11, 36, 41, 2, 17, 0, 0, 0, 1, 170, 201, 19, 183, 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