Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361df084de964544a3bb2e7fcc4cc25b7963e302a4f5ac258ee83d41719e8b96

Tx prefix hash: 04a958a44133d5da73738246e16271ace4345a738a8ab1d5b6596570d1cc058a
Tx public key: 1500f5d9791eaed886126ae864162602b1bd54dbc00afe0ce1de1485a8f4139b
Timestamp: 1737626098 Timestamp [UCT]: 2025-01-23 09:54:58 Age [y:d:h:m:s]: 00:149:11:35:03
Block: 1203483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106534 RingCT/type: yes/0
Extra: 011500f5d9791eaed886126ae864162602b1bd54dbc00afe0ce1de1485a8f4139b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c70a162c83bb21df5654f95ea0e923b446051b9c5575ef872237c3df39c2562a 0.600000000000 1690160 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": 1203493, "vin": [ { "gen": { "height": 1203483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c70a162c83bb21df5654f95ea0e923b446051b9c5575ef872237c3df39c2562a" } } ], "extra": [ 1, 21, 0, 245, 217, 121, 30, 174, 216, 134, 18, 106, 232, 100, 22, 38, 2, 177, 189, 84, 219, 192, 10, 254, 12, 225, 222, 20, 133, 168, 244, 19, 155, 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