Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc2c5581f90746471eefa565d8e4a0177fea00c45bf26aca6c9bfa808008663a

Tx prefix hash: a140c282b5888d5d0c373cf35cfb3e7849ae8bb63e195b6b7bbad51459330fd9
Tx public key: 08b0b03fd2e605c962cc1373cf7319b4d120a86ab25a92d0560e3ee3ed1b44dd
Timestamp: 1706808891 Timestamp [UCT]: 2024-02-01 17:34:51 Age [y:d:h:m:s]: 00:287:18:48:51
Block: 948181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206057 RingCT/type: yes/0
Extra: 0108b0b03fd2e605c962cc1373cf7319b4d120a86ab25a92d0560e3ee3ed1b44dd0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b337ba491466aad2a3ff8a25756e5551cf3f1c4652b7a509c727dd989dc88285 0.600000000000 1406553 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": 948191, "vin": [ { "gen": { "height": 948181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b337ba491466aad2a3ff8a25756e5551cf3f1c4652b7a509c727dd989dc88285" } } ], "extra": [ 1, 8, 176, 176, 63, 210, 230, 5, 201, 98, 204, 19, 115, 207, 115, 25, 180, 209, 32, 168, 106, 178, 90, 146, 208, 86, 14, 62, 227, 237, 27, 68, 221, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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