Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2726672e805e513e42b30d14f208ffc04dc5dfdcb5e710f719590225450f59a1

Tx prefix hash: a17f0958782e1db49c5236b12ec3d250f2e7c94a52d6667bdea9dd66cb431e61
Tx public key: b647338c6a3a44870df788175cf8070ba99a2d6baaa5a71238abdc28db8289fc
Timestamp: 1700350465 Timestamp [UCT]: 2023-11-18 23:34:25 Age [y:d:h:m:s]: 01:212:19:02:18
Block: 894650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413177 RingCT/type: yes/0
Extra: 01b647338c6a3a44870df788175cf8070ba99a2d6baaa5a71238abdc28db8289fc021100000003e08532b6000000000000000000

1 output(s) for total of 0.666274442000 dcy

stealth address amount amount idx
00: f86f7686c40f1cc0b9d17b3d0a6983ceaf38eec86b1e7fabf121f722ad39fe4c 0.666274442000 1350857 of 0

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": 894660, "vin": [ { "gen": { "height": 894650 } } ], "vout": [ { "amount": 666274442, "target": { "key": "f86f7686c40f1cc0b9d17b3d0a6983ceaf38eec86b1e7fabf121f722ad39fe4c" } } ], "extra": [ 1, 182, 71, 51, 140, 106, 58, 68, 135, 13, 247, 136, 23, 92, 248, 7, 11, 169, 154, 45, 107, 170, 165, 167, 18, 56, 171, 220, 40, 219, 130, 137, 252, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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