Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84c57e29ca196bd99712b3629436f4d8b2140ede923eab64f2e9260e029b7081

Tx prefix hash: 7df0479086e2215f2eca5ea32e27948859073986ca733dc593341b6fa9bce41f
Tx public key: b27bf93fb9fbf22e6439aefbd05b17bde53a0cd8e1ef1c1dc346d3d984f1ee53
Timestamp: 1739950630 Timestamp [UCT]: 2025-02-19 07:37:10 Age [y:d:h:m:s]: 00:274:14:50:49
Block: 1222486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194044 RingCT/type: yes/0
Extra: 01b27bf93fb9fbf22e6439aefbd05b17bde53a0cd8e1ef1c1dc346d3d984f1ee530211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78dabed34445563969e40b632e5e75e915018117dc1a8aa05289e0edb56c2790 0.600000000000 1709337 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": 1222496, "vin": [ { "gen": { "height": 1222486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78dabed34445563969e40b632e5e75e915018117dc1a8aa05289e0edb56c2790" } } ], "extra": [ 1, 178, 123, 249, 63, 185, 251, 242, 46, 100, 57, 174, 251, 208, 91, 23, 189, 229, 58, 12, 216, 225, 239, 28, 29, 195, 70, 211, 217, 132, 241, 238, 83, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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