Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76ac28c87d7374e4fff5ea43298440c6da107200958c834a2eb300cb48e5b39d

Tx prefix hash: 828da7b53e59219053550850933f0e64570675d339087c4dc32aa0a2f50626a1
Tx public key: b18fcc11e3c4dc6a91201bcdc1202891fe030bd6d677bda181265b2a7a81091a
Timestamp: 1750656842 Timestamp [UCT]: 2025-06-23 05:34:02 Age [y:d:h:m:s]: 00:143:20:11:36
Block: 1310938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100687 RingCT/type: yes/0
Extra: 01b18fcc11e3c4dc6a91201bcdc1202891fe030bd6d677bda181265b2a7a81091a02110000000e43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af7046cd96ee97b0cb8f6c93502f9f97fb8aa631a13c53bc2e63d2794deb8e5c 0.600000000000 1798561 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": 1310948, "vin": [ { "gen": { "height": 1310938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af7046cd96ee97b0cb8f6c93502f9f97fb8aa631a13c53bc2e63d2794deb8e5c" } } ], "extra": [ 1, 177, 143, 204, 17, 227, 196, 220, 106, 145, 32, 27, 205, 193, 32, 40, 145, 254, 3, 11, 214, 214, 119, 189, 161, 129, 38, 91, 42, 122, 129, 9, 26, 2, 17, 0, 0, 0, 14, 67, 132, 109, 102, 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