Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3431ca5207f71d7343cc28c34a4f70fcd7197a9da0a18fb463eaade07c8e95a1

Tx prefix hash: 978ca984029e519c1c8b24cb610ae61231573873ccc33da3240b1384e662642f
Tx public key: 7225df3113976ff0227ebe6204e439b9b02c7c5c13d509ea1cbd28d0d96e7945
Timestamp: 1737646644 Timestamp [UCT]: 2025-01-23 15:37:24 Age [y:d:h:m:s]: 00:300:22:05:43
Block: 1203664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212602 RingCT/type: yes/0
Extra: 017225df3113976ff0227ebe6204e439b9b02c7c5c13d509ea1cbd28d0d96e79450211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79843f8fe43d160f109d3e515a1166048fb97fb1be05d505df227bbd9a9a7a31 0.600000000000 1690343 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": 1203674, "vin": [ { "gen": { "height": 1203664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79843f8fe43d160f109d3e515a1166048fb97fb1be05d505df227bbd9a9a7a31" } } ], "extra": [ 1, 114, 37, 223, 49, 19, 151, 111, 240, 34, 126, 190, 98, 4, 228, 57, 185, 176, 44, 124, 92, 19, 213, 9, 234, 28, 189, 40, 208, 217, 110, 121, 69, 2, 17, 0, 0, 0, 4, 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