Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd9bfe8feed5901e3330d08a38b077ab83bd31b406bb2fea197e66ff72376d5b

Tx prefix hash: a94f2a2cace1f067b0da11be83e2354ee62c7397c9176745611492d0a9579ecb
Tx public key: 4b7fb704f2219b64be6fc765fb143a25d48a76d28f65b740bba12a8b5dcc5ffa
Timestamp: 1738630067 Timestamp [UCT]: 2025-02-04 00:47:47 Age [y:d:h:m:s]: 00:289:13:42:22
Block: 1211573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204715 RingCT/type: yes/0
Extra: 014b7fb704f2219b64be6fc765fb143a25d48a76d28f65b740bba12a8b5dcc5ffa021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 849ab09769cdae35e770aaf146098b3e392c17fe78b54575b8e1fd1bcee6cd74 0.600000000000 1698334 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": 1211583, "vin": [ { "gen": { "height": 1211573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "849ab09769cdae35e770aaf146098b3e392c17fe78b54575b8e1fd1bcee6cd74" } } ], "extra": [ 1, 75, 127, 183, 4, 242, 33, 155, 100, 190, 111, 199, 101, 251, 20, 58, 37, 212, 138, 118, 210, 143, 101, 183, 64, 187, 161, 42, 139, 93, 204, 95, 250, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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