Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2b643f3ad5d6759af7ce96a37604222b6039dbdc0aa80e1caa3688d3e408fa0

Tx prefix hash: 96063f7bdc683eb2d5082e1dcf38f73b49d7c980a85b82122c34b3261638115e
Tx public key: a1d61addd2fea96ebfe543612ae1d0c19e65c15fe054b80b37041a0c0460bbe2
Timestamp: 1730637759 Timestamp [UCT]: 2024-11-03 12:42:39 Age [y:d:h:m:s]: 01:082:17:59:32
Block: 1145666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317476 RingCT/type: yes/0
Extra: 01a1d61addd2fea96ebfe543612ae1d0c19e65c15fe054b80b37041a0c0460bbe2021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 861104d98ecce8f0f391b0b3cbed94e845e2246347b618f3acfca2eb657e13f0 0.600000000000 1630153 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": 1145676, "vin": [ { "gen": { "height": 1145666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "861104d98ecce8f0f391b0b3cbed94e845e2246347b618f3acfca2eb657e13f0" } } ], "extra": [ 1, 161, 214, 26, 221, 210, 254, 169, 110, 191, 229, 67, 97, 42, 225, 208, 193, 158, 101, 193, 95, 224, 84, 184, 11, 55, 4, 26, 12, 4, 96, 187, 226, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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