Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b10a23c131541fe7e4deb1d3798593eb0e1d4c8f9a6ec9dd39539187447832b

Tx prefix hash: 666f190737b5fa24b733be1afcb9f4f51b963519ca15d2e510f5481aa1f17ca6
Tx public key: 38ab0f165e5c68096e4e1ee59aa1f47d96d29db2dd13dcbf254338093216115a
Timestamp: 1702307954 Timestamp [UCT]: 2023-12-11 15:19:14 Age [y:d:h:m:s]: 01:339:21:37:05
Block: 910883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501787 RingCT/type: yes/0
Extra: 0138ab0f165e5c68096e4e1ee59aa1f47d96d29db2dd13dcbf254338093216115a02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ba5033f22736fa04c938d60baf0931284101496cc1766fce41a96501d9f7725 0.600000000000 1368058 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": 910893, "vin": [ { "gen": { "height": 910883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ba5033f22736fa04c938d60baf0931284101496cc1766fce41a96501d9f7725" } } ], "extra": [ 1, 56, 171, 15, 22, 94, 92, 104, 9, 110, 78, 30, 229, 154, 161, 244, 125, 150, 210, 157, 178, 221, 19, 220, 191, 37, 67, 56, 9, 50, 22, 17, 90, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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