Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4dc4ba9367ba5209087af8fccbdeea5fd0c2c111b28b00f7431de2d3b8b7e6f

Tx prefix hash: 738e521db73168e822803f0b5d50140ccb97209eefad432623372bffe95f2868
Tx public key: 417c243147076fc7d69897f38b3bc1277a35c324dd5ac47bc160f13b1a0a234c
Timestamp: 1717721965 Timestamp [UCT]: 2024-06-07 00:59:25 Age [y:d:h:m:s]: 00:285:09:29:03
Block: 1038667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203974 RingCT/type: yes/0
Extra: 01417c243147076fc7d69897f38b3bc1277a35c324dd5ac47bc160f13b1a0a234c02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97f8957f5dd9e089496497c769bd40d2ee934668b2f8cce44f29dfbbb35790e4 0.600000000000 1507228 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": 1038677, "vin": [ { "gen": { "height": 1038667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97f8957f5dd9e089496497c769bd40d2ee934668b2f8cce44f29dfbbb35790e4" } } ], "extra": [ 1, 65, 124, 36, 49, 71, 7, 111, 199, 214, 152, 151, 243, 139, 59, 193, 39, 122, 53, 195, 36, 221, 90, 196, 123, 193, 96, 241, 59, 26, 10, 35, 76, 2, 17, 0, 0, 0, 10, 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