Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa350e025dcf33de9f2d9f53a8493e95350b4cb4555a85a4cb6374ff94224ee4

Tx prefix hash: 0b6cf43fb2d7f1bed70b139dbaac78ffeb6b89b195829e4d4cf49142c63f46a7
Tx public key: 501c9389de4ea60bcc91b6035b922abf182417f7205c6df156f2b881578da675
Timestamp: 1710294222 Timestamp [UCT]: 2024-03-13 01:43:42 Age [y:d:h:m:s]: 01:030:12:10:04
Block: 977104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282783 RingCT/type: yes/0
Extra: 01501c9389de4ea60bcc91b6035b922abf182417f7205c6df156f2b881578da6750211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8bfb086e0c6b4b7feec4bd86734da8095e9dcd9923161b4dd5c33a955dd33fb 0.600000000000 1437105 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": 977114, "vin": [ { "gen": { "height": 977104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8bfb086e0c6b4b7feec4bd86734da8095e9dcd9923161b4dd5c33a955dd33fb" } } ], "extra": [ 1, 80, 28, 147, 137, 222, 78, 166, 11, 204, 145, 182, 3, 91, 146, 42, 191, 24, 36, 23, 247, 32, 92, 109, 241, 86, 242, 184, 129, 87, 141, 166, 117, 2, 17, 0, 0, 0, 8, 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