Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d471ee4ce7cb5748c2be9c966c2639774919c8369969f2ea7f879befb9a7f2a

Tx prefix hash: 00ed38c3e4e2de55a9843b169d61c0116e67bf58f80263eabd8f5a1b410f5c05
Tx public key: 8ce5d7474c70dbebf5d5f58da9c94b1c475f191fdb4474e19cfcae9ef962b093
Timestamp: 1709319794 Timestamp [UCT]: 2024-03-01 19:03:14 Age [y:d:h:m:s]: 00:329:09:05:15
Block: 969024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235720 RingCT/type: yes/0
Extra: 018ce5d7474c70dbebf5d5f58da9c94b1c475f191fdb4474e19cfcae9ef962b09302110000000149a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63e493e84c6a4fd6e38aed06f92ad9eba1bc7e97245dcd8e490566e0e5d1c512 0.600000000000 1428851 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": 969034, "vin": [ { "gen": { "height": 969024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63e493e84c6a4fd6e38aed06f92ad9eba1bc7e97245dcd8e490566e0e5d1c512" } } ], "extra": [ 1, 140, 229, 215, 71, 76, 112, 219, 235, 245, 213, 245, 141, 169, 201, 75, 28, 71, 95, 25, 31, 219, 68, 116, 225, 156, 252, 174, 158, 249, 98, 176, 147, 2, 17, 0, 0, 0, 1, 73, 161, 133, 187, 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