Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1721a1036a90ee1f2615c7aca3e7290342d7eaa14d0020bc4e0f88dce7b9b549

Tx prefix hash: a7944cd8db38c29bd7a23828d56ada29cfe222b29820bc5246bf2caaf8b5d3f6
Tx public key: a9ecc871f05bffdea7151143f67a8e975e92f1aca0ca8d41c6c1548c08786b38
Timestamp: 1726843104 Timestamp [UCT]: 2024-09-20 14:38:24 Age [y:d:h:m:s]: 00:271:03:16:59
Block: 1114291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193518 RingCT/type: yes/0
Extra: 01a9ecc871f05bffdea7151143f67a8e975e92f1aca0ca8d41c6c1548c08786b38021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 407ddedb24fc1397179b04f54ff8c963a74093e12b4d2f3790af488919a832aa 0.600000000000 1594090 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": 1114301, "vin": [ { "gen": { "height": 1114291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "407ddedb24fc1397179b04f54ff8c963a74093e12b4d2f3790af488919a832aa" } } ], "extra": [ 1, 169, 236, 200, 113, 240, 91, 255, 222, 167, 21, 17, 67, 246, 122, 142, 151, 94, 146, 241, 172, 160, 202, 141, 65, 198, 193, 84, 140, 8, 120, 107, 56, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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