Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 258a239d4576a4e882a16d7560749d74688636db2c7b4cd49edf9b6c380dbc58

Tx prefix hash: 026f99c6cefd3585f98ac7d56e56db87e159a34449c7b06e60406e2b7d04a4ef
Tx public key: 177e61cfcd96f918a435b45d4d31ebfaa8e57e96910a03f94e78de27ee0395a4
Timestamp: 1752139726 Timestamp [UCT]: 2025-07-10 09:28:46 Age [y:d:h:m:s]: 00:166:16:54:12
Block: 1322535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117735 RingCT/type: yes/0
Extra: 01177e61cfcd96f918a435b45d4d31ebfaa8e57e96910a03f94e78de27ee0395a402110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 822291a8fb6ed308aabe3f0b96a7d4b5dafe2fd66c28490d4c0ec8fb59964b76 0.600000000000 1810266 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": 1322545, "vin": [ { "gen": { "height": 1322535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "822291a8fb6ed308aabe3f0b96a7d4b5dafe2fd66c28490d4c0ec8fb59964b76" } } ], "extra": [ 1, 23, 126, 97, 207, 205, 150, 249, 24, 164, 53, 180, 93, 77, 49, 235, 250, 168, 229, 126, 150, 145, 10, 3, 249, 78, 120, 222, 39, 238, 3, 149, 164, 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