Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2de241a3db912f87869f0c41d4bc8d0bcb7004b2939ca1f86cd780259f48e689

Tx prefix hash: a3c60003d9244647a27f2267fe55e58e1ad55c9fe5e9e05e38565ac21c130652
Tx public key: 506c9eea54b73394cbce22d40936d2f9fa9a8d4de5f299bcded509d16ade2a60
Timestamp: 1720255798 Timestamp [UCT]: 2024-07-06 08:49:58 Age [y:d:h:m:s]: 00:302:12:12:59
Block: 1059671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216163 RingCT/type: yes/0
Extra: 01506c9eea54b73394cbce22d40936d2f9fa9a8d4de5f299bcded509d16ade2a6002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 829fcac6514cd3b1dc840dc198b46e110cc92a507d14a1981510e394dae30a42 0.600000000000 1530142 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": 1059681, "vin": [ { "gen": { "height": 1059671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "829fcac6514cd3b1dc840dc198b46e110cc92a507d14a1981510e394dae30a42" } } ], "extra": [ 1, 80, 108, 158, 234, 84, 183, 51, 148, 203, 206, 34, 212, 9, 54, 210, 249, 250, 154, 141, 77, 229, 242, 153, 188, 222, 213, 9, 209, 106, 222, 42, 96, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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