Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74789bca35620e696a9fa1024e520b0667dd6d563efd7b5783bedcb53f876244

Tx prefix hash: 35dc128a64f3e7dde0441133da2d20a0e1f37d556e25af136efa2933b3434332
Tx public key: 330593a63905bebdf32816c054d2e69d40cf3dcfb72a34d41d0c6fe7c3708fe1
Timestamp: 1706050565 Timestamp [UCT]: 2024-01-23 22:56:05 Age [y:d:h:m:s]: 01:084:13:21:04
Block: 941876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321539 RingCT/type: yes/0
Extra: 01330593a63905bebdf32816c054d2e69d40cf3dcfb72a34d41d0c6fe7c3708fe102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f02c9493d3f4fd6ea8d2f21206d6d39ce23e35a414f83b7415d42674a237817 0.600000000000 1400034 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": 941886, "vin": [ { "gen": { "height": 941876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f02c9493d3f4fd6ea8d2f21206d6d39ce23e35a414f83b7415d42674a237817" } } ], "extra": [ 1, 51, 5, 147, 166, 57, 5, 190, 189, 243, 40, 22, 192, 84, 210, 230, 157, 64, 207, 61, 207, 183, 42, 52, 212, 29, 12, 111, 231, 195, 112, 143, 225, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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