Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fad58dd20e3ece84f01fb1922959d56b07f2942ef4e718948558236c8fde5d7f

Tx prefix hash: 2ef20982360e0b465a1be5907d1f70d6e7f284399b2ca0a3d5e3f4d567f7c8bd
Tx public key: 645c3779a8f3ac7c6a37144c68a37821909e3247ac3246482ad721f4784a9761
Timestamp: 1720049224 Timestamp [UCT]: 2024-07-03 23:27:04 Age [y:d:h:m:s]: 00:323:10:22:53
Block: 1057958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231147 RingCT/type: yes/0
Extra: 01645c3779a8f3ac7c6a37144c68a37821909e3247ac3246482ad721f4784a97610211000000040cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5da1cd4b3b7b52390207f38ebdbf515b9a38b1ab70f5d944621c0eccb783b12 0.600000000000 1528401 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": 1057968, "vin": [ { "gen": { "height": 1057958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5da1cd4b3b7b52390207f38ebdbf515b9a38b1ab70f5d944621c0eccb783b12" } } ], "extra": [ 1, 100, 92, 55, 121, 168, 243, 172, 124, 106, 55, 20, 76, 104, 163, 120, 33, 144, 158, 50, 71, 172, 50, 70, 72, 42, 215, 33, 244, 120, 74, 151, 97, 2, 17, 0, 0, 0, 4, 12, 206, 6, 54, 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