Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2df4f40510b4023a38485fed0270bd4dacc50a76922009f6098f75f73690d53

Tx prefix hash: 464ca52c25943906714ac86e82e1f9746cfefcb0576114d831c1725af59a921d
Tx public key: 617bc7e6e34d46ead08b010d6a2f451d7224dfe093a54fbc2ec96b207e887f6a
Timestamp: 1747854494 Timestamp [UCT]: 2025-05-21 19:08:14 Age [y:d:h:m:s]: 00:226:20:52:22
Block: 1287960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159892 RingCT/type: yes/0
Extra: 01617bc7e6e34d46ead08b010d6a2f451d7224dfe093a54fbc2ec96b207e887f6a0211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c028f58a2187164420e97646b05d4b0a7811056a9d5b3cccf58b3e6964f973a 0.600000000000 1775427 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": 1287970, "vin": [ { "gen": { "height": 1287960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c028f58a2187164420e97646b05d4b0a7811056a9d5b3cccf58b3e6964f973a" } } ], "extra": [ 1, 97, 123, 199, 230, 227, 77, 70, 234, 208, 139, 1, 13, 106, 47, 69, 29, 114, 36, 223, 224, 147, 165, 79, 188, 46, 201, 107, 32, 126, 136, 127, 106, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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