Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13fcb6c03ca41db436e24e916f70d99f95340868059cb86946eb5793745b575a

Tx prefix hash: e3b6c9377de2fd1223a78f691ef81b119f959e21a580d33c6201fbfed4713a0b
Tx public key: efcf4e477cd5d1f5f2d2c9298e6d30e0f8736b8371d3a580a1090f47660f7188
Timestamp: 1725955742 Timestamp [UCT]: 2024-09-10 08:09:02 Age [y:d:h:m:s]: 00:119:02:40:36
Block: 1106939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85172 RingCT/type: yes/0
Extra: 01efcf4e477cd5d1f5f2d2c9298e6d30e0f8736b8371d3a580a1090f47660f7188021100000015e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7316470538e7bf304f15e03bb71db2e61f9edb826852bdf8ed449948c1959ba6 0.600000000000 1584544 of 15

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": 1106949, "vin": [ { "gen": { "height": 1106939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7316470538e7bf304f15e03bb71db2e61f9edb826852bdf8ed449948c1959ba6" } } ], "extra": [ 1, 239, 207, 78, 71, 124, 213, 209, 245, 242, 210, 201, 41, 142, 109, 48, 224, 248, 115, 107, 131, 113, 211, 165, 128, 161, 9, 15, 71, 102, 15, 113, 136, 2, 17, 0, 0, 0, 21, 233, 20, 221, 21, 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