Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f73ae3175f29da04e5578523321b7d49c4ca9077b50174239a89daf00049b26

Tx prefix hash: a214cc7d468932b971adb7e8040b310f71bad894906b2d3fde5a6c652eb05a64
Tx public key: 1eb0340c3605b3e8afebf3140e203b19b044be1fbf1f67e2d30f95d42c135753
Timestamp: 1734795068 Timestamp [UCT]: 2024-12-21 15:31:08 Age [y:d:h:m:s]: 00:175:21:04:15
Block: 1180129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125404 RingCT/type: yes/0
Extra: 011eb0340c3605b3e8afebf3140e203b19b044be1fbf1f67e2d30f95d42c135753021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31a44e7c57ba59d4070466b55e7015f4594517733c1859d196c36c7b602f623b 0.600000000000 1666534 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": 1180139, "vin": [ { "gen": { "height": 1180129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31a44e7c57ba59d4070466b55e7015f4594517733c1859d196c36c7b602f623b" } } ], "extra": [ 1, 30, 176, 52, 12, 54, 5, 179, 232, 175, 235, 243, 20, 14, 32, 59, 25, 176, 68, 190, 31, 191, 31, 103, 226, 211, 15, 149, 212, 44, 19, 87, 83, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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