Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ea67f3ba11589c4401555942025db45750e0aa081c9ccaaa4fc0f23a01c96de

Tx prefix hash: 3099582894252dd72db8a94451f5b70834670eb2560a88e545564cc3bf28d08d
Tx public key: 4050ab6f98c8ae7faf94780c0e256b20b363e6686c6e219726f7a2e58cb5a69b
Timestamp: 1710852710 Timestamp [UCT]: 2024-03-19 12:51:50 Age [y:d:h:m:s]: 01:064:23:14:00
Block: 981735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307439 RingCT/type: yes/0
Extra: 014050ab6f98c8ae7faf94780c0e256b20b363e6686c6e219726f7a2e58cb5a69b02110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78bbca5607e2e667a2c45a91028f826fb245509da51f6b9766f8734591b80db3 0.600000000000 1441832 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": 981745, "vin": [ { "gen": { "height": 981735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78bbca5607e2e667a2c45a91028f826fb245509da51f6b9766f8734591b80db3" } } ], "extra": [ 1, 64, 80, 171, 111, 152, 200, 174, 127, 175, 148, 120, 12, 14, 37, 107, 32, 179, 99, 230, 104, 108, 110, 33, 151, 38, 247, 162, 229, 140, 181, 166, 155, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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