Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47822409265ef7718cd49c4b1e88f3d758e5b992d29946680ccb6e189a975c8c

Tx prefix hash: 9f6096d93b933311c163e3dad95afe93ba931178b49452bcc4e9ebfb5043b7ee
Tx public key: c9981771e8583fe0fcb6c81c305e35366591e7391c7868b105d2b49d5fa573db
Timestamp: 1694558830 Timestamp [UCT]: 2023-09-12 22:47:10 Age [y:d:h:m:s]: 01:234:12:06:07
Block: 846818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428713 RingCT/type: yes/0
Extra: 01c9981771e8583fe0fcb6c81c305e35366591e7391c7868b105d2b49d5fa573db02110000000c4b8f5122000000000000000000

1 output(s) for total of 0.959711053000 dcy

stealth address amount amount idx
00: f5d0e081415c45b5e6a4aff8edcc75e9901bde95897ba3880a716cb8e6a0acce 0.959711053000 1300302 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": 846828, "vin": [ { "gen": { "height": 846818 } } ], "vout": [ { "amount": 959711053, "target": { "key": "f5d0e081415c45b5e6a4aff8edcc75e9901bde95897ba3880a716cb8e6a0acce" } } ], "extra": [ 1, 201, 152, 23, 113, 232, 88, 63, 224, 252, 182, 200, 28, 48, 94, 53, 54, 101, 145, 231, 57, 28, 120, 104, 177, 5, 210, 180, 157, 95, 165, 115, 219, 2, 17, 0, 0, 0, 12, 75, 143, 81, 34, 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