Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c94a595b3d1b3341daed301db3249ed48fa03a4dfcebed959581d3a3f2a8464b

Tx prefix hash: 13a15dd0e10e99f9dc83de99455e61a6cc8cc7aa504edf63ab5f55fbe1172ad4
Tx public key: 5b9b6cac186c5b89dcad76ceab04b570a48a82d782fa4f185f9a954ce36081a7
Timestamp: 1695441137 Timestamp [UCT]: 2023-09-23 03:52:17 Age [y:d:h:m:s]: 01:268:00:37:07
Block: 854141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452565 RingCT/type: yes/0
Extra: 015b9b6cac186c5b89dcad76ceab04b570a48a82d782fa4f185f9a954ce36081a702110000000575e3f0e9000000000000000000

1 output(s) for total of 0.907562090000 dcy

stealth address amount amount idx
00: f36ba23537edcd957d3dee440033b16b1a24c734404e0ec619d1208dbc7e1fed 0.907562090000 1308097 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": 854151, "vin": [ { "gen": { "height": 854141 } } ], "vout": [ { "amount": 907562090, "target": { "key": "f36ba23537edcd957d3dee440033b16b1a24c734404e0ec619d1208dbc7e1fed" } } ], "extra": [ 1, 91, 155, 108, 172, 24, 108, 91, 137, 220, 173, 118, 206, 171, 4, 181, 112, 164, 138, 130, 215, 130, 250, 79, 24, 95, 154, 149, 76, 227, 96, 129, 167, 2, 17, 0, 0, 0, 5, 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