Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a2cccc662c6612b23a3b5a88445348364e4440c85184248dfbf7ee59b0ea3aa

Tx prefix hash: 8fc6e0911ac7f19ad10379c90e42c07e6d995f7fda0a970b47a5f37b33b2b3f6
Tx public key: 1b29e29d7dcfbb4d8e4b05022ad1d9c78e8b14010354044200f25fa757d5115e
Timestamp: 1708450543 Timestamp [UCT]: 2024-02-20 17:35:43 Age [y:d:h:m:s]: 01:049:10:43:56
Block: 961802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296374 RingCT/type: yes/0
Extra: 011b29e29d7dcfbb4d8e4b05022ad1d9c78e8b14010354044200f25fa757d5115e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eaa73635369af2ebaefe0b9666380e2162a83c0b3f946d743f9250b3ba26c198 0.600000000000 1421415 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": 961812, "vin": [ { "gen": { "height": 961802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eaa73635369af2ebaefe0b9666380e2162a83c0b3f946d743f9250b3ba26c198" } } ], "extra": [ 1, 27, 41, 226, 157, 125, 207, 187, 77, 142, 75, 5, 2, 42, 209, 217, 199, 142, 139, 20, 1, 3, 84, 4, 66, 0, 242, 95, 167, 87, 213, 17, 94, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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