Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 748254aabb2aef5a45ac2f361a54076b6a18245b13023e26ae4602324713907d

Tx prefix hash: 1f41b9df84f8baed89663f8274aad50feea02c90c589fc345546554e90423a9d
Tx public key: 323eb60eb963760ad13592a224aaf846758bf424a0e2750511f6f3c9c58c3f16
Timestamp: 1760022225 Timestamp [UCT]: 2025-10-09 15:03:45 Age [y:d:h:m:s]: 00:037:08:19:44
Block: 1386241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26746 RingCT/type: yes/0
Extra: 01323eb60eb963760ad13592a224aaf846758bf424a0e2750511f6f3c9c58c3f16021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a892a2a349be9b6b743ee1c5308a6deddc119f518b756b5ac5b90c2a4d029ade 0.600000000000 1874406 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": 1386251, "vin": [ { "gen": { "height": 1386241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a892a2a349be9b6b743ee1c5308a6deddc119f518b756b5ac5b90c2a4d029ade" } } ], "extra": [ 1, 50, 62, 182, 14, 185, 99, 118, 10, 209, 53, 146, 162, 36, 170, 248, 70, 117, 139, 244, 36, 160, 226, 117, 5, 17, 246, 243, 201, 197, 140, 63, 22, 2, 17, 0, 0, 0, 2, 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