Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3c68e9192fa577c33f0a2883cc6532d93e6d57bb3c0b93fc31a6a6cd161cc9b

Tx prefix hash: 671b80cb63c090dfc0715b77d220f4cbaf60ba16488192a508ef8938c40ca7c3
Tx public key: b7478c31a84f9761d3306967d962f07e0e2ae744f23931540e4612fea6730c50
Timestamp: 1754848528 Timestamp [UCT]: 2025-08-10 17:55:28 Age [y:d:h:m:s]: 00:109:11:55:47
Block: 1344293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77475 RingCT/type: yes/0
Extra: 01b7478c31a84f9761d3306967d962f07e0e2ae744f23931540e4612fea6730c50021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ea18a7eb03dae6ce0278bcdcaee12800e83c317c152ef4e033efe1648b2a4ab 0.600000000000 1832176 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": 1344303, "vin": [ { "gen": { "height": 1344293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ea18a7eb03dae6ce0278bcdcaee12800e83c317c152ef4e033efe1648b2a4ab" } } ], "extra": [ 1, 183, 71, 140, 49, 168, 79, 151, 97, 211, 48, 105, 103, 217, 98, 240, 126, 14, 42, 231, 68, 242, 57, 49, 84, 14, 70, 18, 254, 166, 115, 12, 80, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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