Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b2d7bb80583742a4490eb358d3976df3554e3707c897646b39b5503b1bfdf50

Tx prefix hash: 88ef050b6a11b9e3b3247debab1d5d003536d2c68e2ac6df1dc8157cbc9aceba
Tx public key: a7fc69a857e6e5b6e604505bb472c0fd2ca8d86f05c02d36305ca776869cd55e
Timestamp: 1755338331 Timestamp [UCT]: 2025-08-16 09:58:51 Age [y:d:h:m:s]: 00:050:13:30:42
Block: 1347773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35844 RingCT/type: yes/0
Extra: 01a7fc69a857e6e5b6e604505bb472c0fd2ca8d86f05c02d36305ca776869cd55e0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e34dc75bce67eb3d80c17acfb5e21cc6f1020f1066979830a1fa03def0c9aa7 0.600000000000 1835694 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": 1347783, "vin": [ { "gen": { "height": 1347773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e34dc75bce67eb3d80c17acfb5e21cc6f1020f1066979830a1fa03def0c9aa7" } } ], "extra": [ 1, 167, 252, 105, 168, 87, 230, 229, 182, 230, 4, 80, 91, 180, 114, 192, 253, 44, 168, 216, 111, 5, 192, 45, 54, 48, 92, 167, 118, 134, 156, 213, 94, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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