Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f237d25aab055dde40d06fb0e62e31259af7577267c7bedecb261537dee54c6b

Tx prefix hash: c47372570936c8808414721a16dc33b40e43db6df2aae68ed16f5662c49269a6
Tx public key: 40bbcab8aecf49be2a4a7b5f18470edf656eb5a1dd81028fea27df0b3075a4de
Timestamp: 1637516337 Timestamp [UCT]: 2021-11-21 17:38:57 Age [y:d:h:m:s]: 03:057:20:19:04
Block: 379134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 820220 RingCT/type: yes/0
Extra: 0140bbcab8aecf49be2a4a7b5f18470edf656eb5a1dd81028fea27df0b3075a4de021100000001536c63bb000000000000000000

1 output(s) for total of 34.022956820000 dcy

stealth address amount amount idx
00: d7aa51c4c12b9e5ea526d96163562b6eb0bc0325a4878bdc2fd3b2cdde6d331d 34.022956820000 766470 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": 379144, "vin": [ { "gen": { "height": 379134 } } ], "vout": [ { "amount": 34022956820, "target": { "key": "d7aa51c4c12b9e5ea526d96163562b6eb0bc0325a4878bdc2fd3b2cdde6d331d" } } ], "extra": [ 1, 64, 187, 202, 184, 174, 207, 73, 190, 42, 74, 123, 95, 24, 71, 14, 223, 101, 110, 181, 161, 221, 129, 2, 143, 234, 39, 223, 11, 48, 117, 164, 222, 2, 17, 0, 0, 0, 1, 83, 108, 99, 187, 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