Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 380f8b529ef3a6caa98fca542c0535e22ec0d7124a0fb3c2dd96f3847f93a1d9

Tx prefix hash: b9714450909fca7bb374e0030fce46a4dac15b6677eb13421442007adf89bef2
Tx public key: ae5c8a749de9bdf6e937ff2f40bdc65c9af01519bf2aa3df8c4eac9660549da2
Timestamp: 1658616770 Timestamp [UCT]: 2022-07-23 22:52:50 Age [y:d:h:m:s]: 02:246:11:02:07
Block: 550270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 697331 RingCT/type: yes/0
Extra: 01ae5c8a749de9bdf6e937ff2f40bdc65c9af01519bf2aa3df8c4eac9660549da20211000000016570b1ef000000000000000000

1 output(s) for total of 9.219920874000 dcy

stealth address amount amount idx
00: a613cb050ebfe3f0f7d4bdb945328d2d4a0275eb3cb1579d043a65354a6f9dcb 9.219920874000 981731 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": 550280, "vin": [ { "gen": { "height": 550270 } } ], "vout": [ { "amount": 9219920874, "target": { "key": "a613cb050ebfe3f0f7d4bdb945328d2d4a0275eb3cb1579d043a65354a6f9dcb" } } ], "extra": [ 1, 174, 92, 138, 116, 157, 233, 189, 246, 233, 55, 255, 47, 64, 189, 198, 92, 154, 240, 21, 25, 191, 42, 163, 223, 140, 78, 172, 150, 96, 84, 157, 162, 2, 17, 0, 0, 0, 1, 101, 112, 177, 239, 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