Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 103bf1bc642c878c23a2b2acfa37d32fc95f428f0975d23ac42550906649dcb5

Tx prefix hash: d3e89a1ccfabdd7fd48c36615b860cf6117f7d5eeab2b47ed09f47027d50bc69
Tx public key: ed4d0d9d1f14c04ed9bb824b685c458f39dd745e9571b1258bd1518171d7c77d
Timestamp: 1729036248 Timestamp [UCT]: 2024-10-15 23:50:48 Age [y:d:h:m:s]: 00:000:23:31:42
Block: 1132491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 685 RingCT/type: yes/0
Extra: 01ed4d0d9d1f14c04ed9bb824b685c458f39dd745e9571b1258bd1518171d7c77d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fd1ade74f1d6b049daccbaa9d3e3a6c2607a02f2f0bbb8724dd60d85432edcd 0.600000000000 1615408 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": 1132501, "vin": [ { "gen": { "height": 1132491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fd1ade74f1d6b049daccbaa9d3e3a6c2607a02f2f0bbb8724dd60d85432edcd" } } ], "extra": [ 1, 237, 77, 13, 157, 31, 20, 192, 78, 217, 187, 130, 75, 104, 92, 69, 143, 57, 221, 116, 94, 149, 113, 177, 37, 139, 209, 81, 129, 113, 215, 199, 125, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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