Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51f3f22e74d68d92412377a539561a6c073433155c5ca9d4b6f6617978677199

Tx prefix hash: 35659ed7ecc829076fdf7b3f1db0afb29d9c527387fb1836e730259b2cf2e00b
Tx public key: b9078f103d660dc3e7db9d42f87117bb473701ca78383bf46a9021b2d6864520
Timestamp: 1578930261 Timestamp [UCT]: 2020-01-13 15:44:21 Age [y:d:h:m:s]: 05:082:16:52:40
Block: 44775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1209236 RingCT/type: yes/0
Extra: 01b9078f103d660dc3e7db9d42f87117bb473701ca78383bf46a9021b2d68645200211000000074943cd9f000000000000000000

1 output(s) for total of 436.171870953000 dcy

stealth address amount amount idx
00: 00a0523d267d53678dd85c932379f059d0ef3e3d1d88fd7b728c7c2d23eccdbb 436.171870953000 81562 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": 44785, "vin": [ { "gen": { "height": 44775 } } ], "vout": [ { "amount": 436171870953, "target": { "key": "00a0523d267d53678dd85c932379f059d0ef3e3d1d88fd7b728c7c2d23eccdbb" } } ], "extra": [ 1, 185, 7, 143, 16, 61, 102, 13, 195, 231, 219, 157, 66, 248, 113, 23, 187, 71, 55, 1, 202, 120, 56, 59, 244, 106, 144, 33, 178, 214, 134, 69, 32, 2, 17, 0, 0, 0, 7, 73, 67, 205, 159, 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