Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52f9bdd366c97989f5e9abf3fa5bb3c9bcdcbef8f675626383974de5a6bf1877

Tx prefix hash: 40bb42603e2483912341caf6ed0f29a96b354ece4a25842396c241bc0e11a52a
Tx public key: 3eb825ccde675bdda87486cbf8c019e70d2962b8150f0cc129c8c7b1fa1a0457
Timestamp: 1577055095 Timestamp [UCT]: 2019-12-22 22:51:35 Age [y:d:h:m:s]: 05:082:02:36:03
Block: 29764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1208309 RingCT/type: yes/0
Extra: 013eb825ccde675bdda87486cbf8c019e70d2962b8150f0cc129c8c7b1fa1a04570211000000144ac5aa02000000000000000000

1 output(s) for total of 489.080530948000 dcy

stealth address amount amount idx
00: 8f4926d2727a25a0ccc17f65fe1930489b6d6128d30af2a9804bd493abac8d39 489.080530948000 49036 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": 29774, "vin": [ { "gen": { "height": 29764 } } ], "vout": [ { "amount": 489080530948, "target": { "key": "8f4926d2727a25a0ccc17f65fe1930489b6d6128d30af2a9804bd493abac8d39" } } ], "extra": [ 1, 62, 184, 37, 204, 222, 103, 91, 221, 168, 116, 134, 203, 248, 192, 25, 231, 13, 41, 98, 184, 21, 15, 12, 193, 41, 200, 199, 177, 250, 26, 4, 87, 2, 17, 0, 0, 0, 20, 74, 197, 170, 2, 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