Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 033ec4883e6267d900f225561e41fa47bad7bbefce40ebf54506755953987e54

Tx prefix hash: e2ef9a91f14bacccc5c0e6a923e71e198d83b8f80026f3d44f56c6f978fbee0f
Tx public key: 0ca6cee13866c53765a8d10ca3cc82dfb147e23a18866ad7b346c5b85a798914
Timestamp: 1750864297 Timestamp [UCT]: 2025-06-25 15:11:37 Age [y:d:h:m:s]: 00:148:03:45:52
Block: 1312590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103839 RingCT/type: yes/0
Extra: 010ca6cee13866c53765a8d10ca3cc82dfb147e23a18866ad7b346c5b85a798914021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 117ca8340fcb9b6e52e8a1d110182a79b4f5dc80e61330170dbd1f57c6eec4e9 0.600000000000 1800223 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": 1312600, "vin": [ { "gen": { "height": 1312590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "117ca8340fcb9b6e52e8a1d110182a79b4f5dc80e61330170dbd1f57c6eec4e9" } } ], "extra": [ 1, 12, 166, 206, 225, 56, 102, 197, 55, 101, 168, 209, 12, 163, 204, 130, 223, 177, 71, 226, 58, 24, 134, 106, 215, 179, 70, 197, 184, 90, 121, 137, 20, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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