Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec2140d116af2038b288414d5af1c69ba6cbae2a57744dfb1645edc4cfc9c1cf

Tx prefix hash: 4619004b5c3d17dfca13d72f229af907b5372fa016a3a431debf7047736b2bc3
Tx public key: 4f6bae86dc977fa525cde949c3e376ca9f153ee4f94c966fdf5d46e58857b156
Timestamp: 1725056753 Timestamp [UCT]: 2024-08-30 22:25:53 Age [y:d:h:m:s]: 00:290:05:48:19
Block: 1099468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207234 RingCT/type: yes/0
Extra: 014f6bae86dc977fa525cde949c3e376ca9f153ee4f94c966fdf5d46e58857b156021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4865c44c19b6ef7c2a3444a96efcd8d500dcabaf09338e41b3e48b5a0c443af9 0.600000000000 1575429 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": 1099478, "vin": [ { "gen": { "height": 1099468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4865c44c19b6ef7c2a3444a96efcd8d500dcabaf09338e41b3e48b5a0c443af9" } } ], "extra": [ 1, 79, 107, 174, 134, 220, 151, 127, 165, 37, 205, 233, 73, 195, 227, 118, 202, 159, 21, 62, 228, 249, 76, 150, 111, 223, 93, 70, 229, 136, 87, 177, 86, 2, 17, 0, 0, 0, 7, 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