Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4482cfcb4ed95b276e54d7ee01af32b9d68b8ed98f29055a39b338296d5aeb8

Tx prefix hash: 3439cd09fdf20582fc0e43c72d41b7d1ead40a4f9c7e544fe10f91b736f0799d
Tx public key: 866f8da34afd7fbf8b1c154e1dd605dd328508cbb506e6f82b1c8323ccb6f610
Timestamp: 1712939506 Timestamp [UCT]: 2024-04-12 16:31:46 Age [y:d:h:m:s]: 00:225:22:07:05
Block: 999004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161746 RingCT/type: yes/0
Extra: 01866f8da34afd7fbf8b1c154e1dd605dd328508cbb506e6f82b1c8323ccb6f61002110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31f2276e693722302135f80957cf1d724ad77c034a8773182a46f34e15f19cd5 0.600000000000 1459480 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": 999014, "vin": [ { "gen": { "height": 999004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31f2276e693722302135f80957cf1d724ad77c034a8773182a46f34e15f19cd5" } } ], "extra": [ 1, 134, 111, 141, 163, 74, 253, 127, 191, 139, 28, 21, 78, 29, 214, 5, 221, 50, 133, 8, 203, 181, 6, 230, 248, 43, 28, 131, 35, 204, 182, 246, 16, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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