Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d116fe4d34a657e3fa5f035f6641b1906b42860e33f1727d91f05a80527fa41

Tx prefix hash: f8369698a57675d1a8a850743bea51157d5d48fb2216358ee3651e94e6d8761f
Tx public key: 1afce4ef9db7657f33ca3b6d3d37af2db4c56d7d809ce2be961016bd5ed4b314
Timestamp: 1731351124 Timestamp [UCT]: 2024-11-11 18:52:04 Age [y:d:h:m:s]: 00:156:22:14:44
Block: 1151564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111990 RingCT/type: yes/0
Extra: 011afce4ef9db7657f33ca3b6d3d37af2db4c56d7d809ce2be961016bd5ed4b3140211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd901a8e150a5324bbe7fda3dec03f3ca8de540b482512be6617fd84b84daefd 0.600000000000 1637121 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": 1151574, "vin": [ { "gen": { "height": 1151564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd901a8e150a5324bbe7fda3dec03f3ca8de540b482512be6617fd84b84daefd" } } ], "extra": [ 1, 26, 252, 228, 239, 157, 183, 101, 127, 51, 202, 59, 109, 61, 55, 175, 45, 180, 197, 109, 125, 128, 156, 226, 190, 150, 16, 22, 189, 94, 212, 179, 20, 2, 17, 0, 0, 0, 2, 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