Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ef3b4a2b81f5625c11b4558980a522c4c691d98df10622091d2439d83d10c84

Tx prefix hash: c7afb796ba01d4ab6a855e523c81ac22a2756af4cecc82039cfef5f586dd40dc
Tx public key: caa01b4897cf6efb209af515cbc670e72a4ef4a89a7076cb6e1c31c2d6031e74
Timestamp: 1762352365 Timestamp [UCT]: 2025-11-05 14:19:25 Age [y:d:h:m:s]: 00:064:06:26:07
Block: 1405544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46034 RingCT/type: yes/0
Extra: 01caa01b4897cf6efb209af515cbc670e72a4ef4a89a7076cb6e1c31c2d6031e7402110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46c7396e863970c6e3f8529fe0fe8ec16cc40169caff8a1fdd58e4d72dbbb295 0.600000000000 1893921 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": 1405554, "vin": [ { "gen": { "height": 1405544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46c7396e863970c6e3f8529fe0fe8ec16cc40169caff8a1fdd58e4d72dbbb295" } } ], "extra": [ 1, 202, 160, 27, 72, 151, 207, 110, 251, 32, 154, 245, 21, 203, 198, 112, 231, 42, 78, 244, 168, 154, 112, 118, 203, 110, 28, 49, 194, 214, 3, 30, 116, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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