Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55aabf3f84e69c142950b9e9b06f05694ab38e364ea3f82f307b2e0284659782

Tx prefix hash: 608c1df29bade51f44ff9c12cb789f8f39e023598fd541a83deef19733b2c222
Tx public key: c971f46b4a2d83677609936e350dd02a6fb5e4ec968eb0da3faa76e4a1688509
Timestamp: 1725541438 Timestamp [UCT]: 2024-09-05 13:03:58 Age [y:d:h:m:s]: 00:252:11:45:16
Block: 1103503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180311 RingCT/type: yes/0
Extra: 01c971f46b4a2d83677609936e350dd02a6fb5e4ec968eb0da3faa76e4a168850902110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b03b84eafdad97b90b9c9645410d2df91a452675b11a3865884872e5ac413eb8 0.600000000000 1580356 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": 1103513, "vin": [ { "gen": { "height": 1103503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b03b84eafdad97b90b9c9645410d2df91a452675b11a3865884872e5ac413eb8" } } ], "extra": [ 1, 201, 113, 244, 107, 74, 45, 131, 103, 118, 9, 147, 110, 53, 13, 208, 42, 111, 181, 228, 236, 150, 142, 176, 218, 63, 170, 118, 228, 161, 104, 133, 9, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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