Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 034d033f4dcb57e206caa11ecd0a83992de365523b06298bd4865d513930d653

Tx prefix hash: ea4cb466c03b2e866afaa54b70af8c9d0db0b666a76079a9e83582b788dcb675
Tx public key: 7d1efb9e2e7b10ef06a7b5152f2166c5c37dd6854b9ce173771b744d724dbe62
Timestamp: 1721618615 Timestamp [UCT]: 2024-07-22 03:23:35 Age [y:d:h:m:s]: 00:217:23:44:49
Block: 1070965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155683 RingCT/type: yes/0
Extra: 017d1efb9e2e7b10ef06a7b5152f2166c5c37dd6854b9ce173771b744d724dbe62021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9218705a7108bce52536f7caae0f3b5f61e29eab1fb4fac2a9bebe73d50ecfce 0.600000000000 1543012 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": 1070975, "vin": [ { "gen": { "height": 1070965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9218705a7108bce52536f7caae0f3b5f61e29eab1fb4fac2a9bebe73d50ecfce" } } ], "extra": [ 1, 125, 30, 251, 158, 46, 123, 16, 239, 6, 167, 181, 21, 47, 33, 102, 197, 195, 125, 214, 133, 75, 156, 225, 115, 119, 27, 116, 77, 114, 77, 190, 98, 2, 17, 0, 0, 0, 2, 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