Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24c808808691fe3cd0660e9241c0395a6e36a7ae581b4a91af5abf7236ff6c7a

Tx prefix hash: fd46297e256eb5cd94643278c4897bc7bb7d993b1b8d528fee1f6af5cb156d87
Tx public key: b14869fbb8086d221036a808f425ecc433edf8acfe9a5d05dc8641605b2bfbf2
Timestamp: 1714794023 Timestamp [UCT]: 2024-05-04 03:40:23 Age [y:d:h:m:s]: 00:250:08:38:50
Block: 1014399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179197 RingCT/type: yes/0
Extra: 01b14869fbb8086d221036a808f425ecc433edf8acfe9a5d05dc8641605b2bfbf20211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bd2ff0d399902cda1ffd35ef20f7730ff24c2a40ab2f19673fdb018e5f1ff3f 0.600000000000 1477480 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": 1014409, "vin": [ { "gen": { "height": 1014399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bd2ff0d399902cda1ffd35ef20f7730ff24c2a40ab2f19673fdb018e5f1ff3f" } } ], "extra": [ 1, 177, 72, 105, 251, 184, 8, 109, 34, 16, 54, 168, 8, 244, 37, 236, 196, 51, 237, 248, 172, 254, 154, 93, 5, 220, 134, 65, 96, 91, 43, 251, 242, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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