Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3364d8491adb4d110cce674199ab2dccaa89a31f883e1f39848b36ba7f92826

Tx prefix hash: c8a74cafcb59306a3d12662609934f3eb910a12adc334fd07c0f8e096ad9f137
Tx public key: bb9cb7c93a857fa589822ceb0231e85e4d96782ea62114565297ded0397dc172
Timestamp: 1574491854 Timestamp [UCT]: 2019-11-23 06:50:54 Age [y:d:h:m:s]: 05:038:08:31:19
Block: 15168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1170633 RingCT/type: yes/0
Extra: 01bb9cb7c93a857fa589822ceb0231e85e4d96782ea62114565297ded0397dc172021100000021d50ca400000000000000000000

1 output(s) for total of 546.692358343000 dcy

stealth address amount amount idx
00: 23a4fd975c57ffad5ee84ed4a4782f854d05d08e6c96cb6dfdc47a12437f3fb5 546.692358343000 20090 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": 15178, "vin": [ { "gen": { "height": 15168 } } ], "vout": [ { "amount": 546692358343, "target": { "key": "23a4fd975c57ffad5ee84ed4a4782f854d05d08e6c96cb6dfdc47a12437f3fb5" } } ], "extra": [ 1, 187, 156, 183, 201, 58, 133, 127, 165, 137, 130, 44, 235, 2, 49, 232, 94, 77, 150, 120, 46, 166, 33, 20, 86, 82, 151, 222, 208, 57, 125, 193, 114, 2, 17, 0, 0, 0, 33, 213, 12, 164, 0, 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