Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88c4e5055ebc5697401b03e759ec3d71f7af2e12d89ccd44b701caa6cd59b0bd

Tx prefix hash: 998bf373a90f6da8b9cbee5a476c099da984ac5959412a305cd52b533a5b363a
Tx public key: c05ee7f56e636b83dcda3c398d3c55ebb7322ffc31b253a73e562db2f94264bf
Timestamp: 1582901925 Timestamp [UCT]: 2020-02-28 14:58:45 Age [y:d:h:m:s]: 05:246:15:03:15
Block: 73499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1328238 RingCT/type: yes/0
Extra: 01c05ee7f56e636b83dcda3c398d3c55ebb7322ffc31b253a73e562db2f94264bf0211000000044943cd9f000000000000000000

1 output(s) for total of 350.328596580000 dcy

stealth address amount amount idx
00: d32430e631d42cbb4885b4b38b3ef51b893af28839370662e03b1559b1e1293d 350.328596580000 135596 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": 73509, "vin": [ { "gen": { "height": 73499 } } ], "vout": [ { "amount": 350328596580, "target": { "key": "d32430e631d42cbb4885b4b38b3ef51b893af28839370662e03b1559b1e1293d" } } ], "extra": [ 1, 192, 94, 231, 245, 110, 99, 107, 131, 220, 218, 60, 57, 141, 60, 85, 235, 183, 50, 47, 252, 49, 178, 83, 167, 62, 86, 45, 178, 249, 66, 100, 191, 2, 17, 0, 0, 0, 4, 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