Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddbed877b4a3e29c530070d157068c7f5ff405d3610d92cc59ad515a63634091

Tx prefix hash: 1d7888ff79b52cff1c2438c1281e476e8dd6d26fd7dbd3ee61d309fc49c1f470
Tx public key: fe60a4e5966f937807679c5f27d4aa074fafb384c77f5092c981c27f3d6e15b3
Timestamp: 1721710178 Timestamp [UCT]: 2024-07-23 04:49:38 Age [y:d:h:m:s]: 00:254:20:12:20
Block: 1071725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182059 RingCT/type: yes/0
Extra: 01fe60a4e5966f937807679c5f27d4aa074fafb384c77f5092c981c27f3d6e15b3021100000008e914dd15000000000000000000

1 output(s) for total of 0.607820000000 dcy

stealth address amount amount idx
00: a1c079272bfa6b974e4f8a0d9d33ee04f05d829ac668cff379b7e8616f8e2456 0.607820000000 1544058 of 0

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": 1071735, "vin": [ { "gen": { "height": 1071725 } } ], "vout": [ { "amount": 607820000, "target": { "key": "a1c079272bfa6b974e4f8a0d9d33ee04f05d829ac668cff379b7e8616f8e2456" } } ], "extra": [ 1, 254, 96, 164, 229, 150, 111, 147, 120, 7, 103, 156, 95, 39, 212, 170, 7, 79, 175, 179, 132, 199, 127, 80, 146, 201, 129, 194, 127, 61, 110, 21, 179, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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