Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92b8fc50de00d94aee8d4e3ee0d698086d5f6a86fb2dbd609f14852b8d763647

Tx prefix hash: 94ac1059f5bb7689ffc6f83de970c51e7e204654c7e59bd1b354139cb71a0ce6
Tx public key: 38f24987c0a2ae9d0d62268017dcc499b6ff1faf34510aa1c0858398215e6326
Timestamp: 1750084061 Timestamp [UCT]: 2025-06-16 14:27:41 Age [y:d:h:m:s]: 00:156:16:42:34
Block: 1306300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109774 RingCT/type: yes/0
Extra: 0138f24987c0a2ae9d0d62268017dcc499b6ff1faf34510aa1c0858398215e632602110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94ecc4771a2e68a1269020061a63e3029a32422e186fe397b40c070e7abff8b2 0.600000000000 1793905 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": 1306310, "vin": [ { "gen": { "height": 1306300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94ecc4771a2e68a1269020061a63e3029a32422e186fe397b40c070e7abff8b2" } } ], "extra": [ 1, 56, 242, 73, 135, 192, 162, 174, 157, 13, 98, 38, 128, 23, 220, 196, 153, 182, 255, 31, 175, 52, 81, 10, 161, 192, 133, 131, 152, 33, 94, 99, 38, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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