Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4bcc17b32b6bbce7987635d6dc95426f8571ccbbffd2439f699fd6eacd97422

Tx prefix hash: 5f4369087daf65403635e62d38568c3027e2d2ddb1fc510d4e4941fca03f25f2
Tx public key: f342a0c7a19c121de3bbeddd3e77d7f78b8b737faf0cabf53f85ba6051fd0e2b
Timestamp: 1721995834 Timestamp [UCT]: 2024-07-26 12:10:34 Age [y:d:h:m:s]: 01:156:20:26:29
Block: 1074093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370677 RingCT/type: yes/0
Extra: 01f342a0c7a19c121de3bbeddd3e77d7f78b8b737faf0cabf53f85ba6051fd0e2b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1ea63686e9544038a090cfd656adf839272a5d6dcf63fa78cef436c26b005d1 0.600000000000 1546606 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": 1074103, "vin": [ { "gen": { "height": 1074093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1ea63686e9544038a090cfd656adf839272a5d6dcf63fa78cef436c26b005d1" } } ], "extra": [ 1, 243, 66, 160, 199, 161, 156, 18, 29, 227, 187, 237, 221, 62, 119, 215, 247, 139, 139, 115, 127, 175, 12, 171, 245, 63, 133, 186, 96, 81, 253, 14, 43, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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