Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13779e7b4f2d9dfc81d126c1bc105e10afb4ccb93b62cf101ab6c8608cc19eef

Tx prefix hash: 0d6eaa3f23982818adc9f9283cd6fa81c39724f685bb5c8306add25f658ed79e
Tx public key: 4fd3e8f74cc72c09f20f8f09b2e67054b89dc23081bae2f4a5dc429ab4a01ba9
Timestamp: 1732807354 Timestamp [UCT]: 2024-11-28 15:22:34 Age [y:d:h:m:s]: 00:122:21:09:13
Block: 1163645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87619 RingCT/type: yes/0
Extra: 014fd3e8f74cc72c09f20f8f09b2e67054b89dc23081bae2f4a5dc429ab4a01ba90211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8517f8db9f65d77cf143a7c3d5104ed2247a6e6416adf74c206cfc1a7a3dbba5 0.600000000000 1649312 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": 1163655, "vin": [ { "gen": { "height": 1163645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8517f8db9f65d77cf143a7c3d5104ed2247a6e6416adf74c206cfc1a7a3dbba5" } } ], "extra": [ 1, 79, 211, 232, 247, 76, 199, 44, 9, 242, 15, 143, 9, 178, 230, 112, 84, 184, 157, 194, 48, 129, 186, 226, 244, 165, 220, 66, 154, 180, 160, 27, 169, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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