Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4636fb67ebaf4e7d0d08701ea9909e526f88bcdaf587d78c1f87cb48a4129a5e

Tx prefix hash: bf27ae12b518e64ac7fdf34e00262ec87339f95c2cd8b497da36deada0ba430a
Tx public key: 08472db8c0bcda53c3cb82d462635baf1a1bb60934b023ba75d8a801cd60df2f
Timestamp: 1702887141 Timestamp [UCT]: 2023-12-18 08:12:21 Age [y:d:h:m:s]: 01:182:16:37:55
Block: 915684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391618 RingCT/type: yes/0
Extra: 0108472db8c0bcda53c3cb82d462635baf1a1bb60934b023ba75d8a801cd60df2f02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d9046def670c5a7ec76874bd462ce4caf72890ac8f959ae727ec8cac8683547 0.600000000000 1373096 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": 915694, "vin": [ { "gen": { "height": 915684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d9046def670c5a7ec76874bd462ce4caf72890ac8f959ae727ec8cac8683547" } } ], "extra": [ 1, 8, 71, 45, 184, 192, 188, 218, 83, 195, 203, 130, 212, 98, 99, 91, 175, 26, 27, 182, 9, 52, 176, 35, 186, 117, 216, 168, 1, 205, 96, 223, 47, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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