Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc867ac06f10a3ce0d48ec62376f1bba2166ef92c9b2dd0f0ecd4d20c6c692e9

Tx prefix hash: fab07760d3ad5717701b69909c87b423c64b636b9faba3726b4f85686d64b7e8
Tx public key: ea9eab9eecedfc04d8d48c5b17e910f371b2b87f46e6904c0333cf8b57137081
Timestamp: 1751032473 Timestamp [UCT]: 2025-06-27 13:54:33 Age [y:d:h:m:s]: 00:145:14:52:57
Block: 1313891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102120 RingCT/type: yes/0
Extra: 01ea9eab9eecedfc04d8d48c5b17e910f371b2b87f46e6904c0333cf8b57137081021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b0c244ef527def6bd609835fd26b3841f8b7a55a145ca031e2d6b5185618740 0.600000000000 1801534 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": 1313901, "vin": [ { "gen": { "height": 1313891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b0c244ef527def6bd609835fd26b3841f8b7a55a145ca031e2d6b5185618740" } } ], "extra": [ 1, 234, 158, 171, 158, 236, 237, 252, 4, 216, 212, 140, 91, 23, 233, 16, 243, 113, 178, 184, 127, 70, 230, 144, 76, 3, 51, 207, 139, 87, 19, 112, 129, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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