Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ffc38ed7b9d420dd1f1d2e7b7122a0b4c1cd8f796aebf2184dd039770695a95

Tx prefix hash: 6c5d5213ed7036cd1b8e884eac0926009b4671738007718ae5e5669d38ec5205
Tx public key: bd6485a3e001e096696c33b6a3e988a4ab826be78b4f081a3f67993365bf5b81
Timestamp: 1738157199 Timestamp [UCT]: 2025-01-29 13:26:39 Age [y:d:h:m:s]: 00:139:06:03:20
Block: 1207668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99482 RingCT/type: yes/0
Extra: 01bd6485a3e001e096696c33b6a3e988a4ab826be78b4f081a3f67993365bf5b810211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b21128554edcd3bd8a1e418c013675dedd8070bd0df0d3790d5c371ebee42623 0.600000000000 1694393 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": 1207678, "vin": [ { "gen": { "height": 1207668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b21128554edcd3bd8a1e418c013675dedd8070bd0df0d3790d5c371ebee42623" } } ], "extra": [ 1, 189, 100, 133, 163, 224, 1, 224, 150, 105, 108, 51, 182, 163, 233, 136, 164, 171, 130, 107, 231, 139, 79, 8, 26, 63, 103, 153, 51, 101, 191, 91, 129, 2, 17, 0, 0, 0, 1, 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