Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 573f544f49346c29f73fdb9b123beafba4e9cec07ccb9b0f780a0801eb4e3334

Tx prefix hash: f1d1b184a64bd44a23f141f08cec274170eba263c8d6d98772b5a577c889797f
Tx public key: cc278c542ce3ef0a7212e782177a2d6c504274ba2d1233d6191624072018ca2a
Timestamp: 1730704565 Timestamp [UCT]: 2024-11-04 07:16:05 Age [y:d:h:m:s]: 00:066:01:58:09
Block: 1146218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47280 RingCT/type: yes/0
Extra: 01cc278c542ce3ef0a7212e782177a2d6c504274ba2d1233d6191624072018ca2a02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f128dfa8f1cb1074fc7f5aac35b421653080c8d4b6de15590e360f9ec8a41b46 0.600000000000 1630813 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": 1146228, "vin": [ { "gen": { "height": 1146218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f128dfa8f1cb1074fc7f5aac35b421653080c8d4b6de15590e360f9ec8a41b46" } } ], "extra": [ 1, 204, 39, 140, 84, 44, 227, 239, 10, 114, 18, 231, 130, 23, 122, 45, 108, 80, 66, 116, 186, 45, 18, 51, 214, 25, 22, 36, 7, 32, 24, 202, 42, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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