Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5012acac719e3b02fe762831f41f6a58df72d08dec1a690247ab46e7d9c8b20

Tx prefix hash: 51bcba8c923d88355236973838e619e6d8bd8c5a4f1cd5f554de2129f9f5be60
Tx public key: ef2554e9e083dbff1b08bdff212a89d5b99233818aae3e64136716e31a2127cf
Timestamp: 1751339252 Timestamp [UCT]: 2025-07-01 03:07:32 Age [y:d:h:m:s]: 00:143:07:25:06
Block: 1316272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100617 RingCT/type: yes/0
Extra: 01ef2554e9e083dbff1b08bdff212a89d5b99233818aae3e64136716e31a2127cf0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80884f5260569b4f525e6f669c865500b51c1ef0c6b97ea69881e85c974752f1 0.600000000000 1803931 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": 1316282, "vin": [ { "gen": { "height": 1316272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80884f5260569b4f525e6f669c865500b51c1ef0c6b97ea69881e85c974752f1" } } ], "extra": [ 1, 239, 37, 84, 233, 224, 131, 219, 255, 27, 8, 189, 255, 33, 42, 137, 213, 185, 146, 51, 129, 138, 174, 62, 100, 19, 103, 22, 227, 26, 33, 39, 207, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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