Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58de7469cb6a5f0e10b0bbf3158e9324b6e3a6614d33e8c7bfbbc3834fa8438c

Tx prefix hash: 876499800fe4732594ff0a68a0d3bfdb9e59d390a90b945f4a0eefda9242e44b
Tx public key: 475ba2ca400baf98bcd51582767f57f87d671b4a480bbccd93e3a9ad819286cb
Timestamp: 1752084849 Timestamp [UCT]: 2025-07-09 18:14:09 Age [y:d:h:m:s]: 00:181:17:34:59
Block: 1322084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128507 RingCT/type: yes/0
Extra: 01475ba2ca400baf98bcd51582767f57f87d671b4a480bbccd93e3a9ad819286cb021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dcd1e1149442050dd88f2cb980e8cafb12e66c31ff9cb635ae2bd2c18f63118 0.600000000000 1809797 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": 1322094, "vin": [ { "gen": { "height": 1322084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dcd1e1149442050dd88f2cb980e8cafb12e66c31ff9cb635ae2bd2c18f63118" } } ], "extra": [ 1, 71, 91, 162, 202, 64, 11, 175, 152, 188, 213, 21, 130, 118, 127, 87, 248, 125, 103, 27, 74, 72, 11, 188, 205, 147, 227, 169, 173, 129, 146, 134, 203, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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