Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 915c75fb077a85ef5273744dcc0f72f54389e6228ccbfa50dff5f1397c9954de

Tx prefix hash: 664e6c2894a1962699513f11cf9936ae4b8536d99e07cc6ab3f4619201493554
Tx public key: f38a8b79eb670c3541ed98472bb1c0cb1c039e9743e2207e8e64250bf2928e0b
Timestamp: 1648237866 Timestamp [UCT]: 2022-03-25 19:51:06 Age [y:d:h:m:s]: 02:324:15:18:41
Block: 466310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 751301 RingCT/type: yes/0
Extra: 01f38a8b79eb670c3541ed98472bb1c0cb1c039e9743e2207e8e64250bf2928e0b021100000002a272b9cb000000000000000000

1 output(s) for total of 17.495310331000 dcy

stealth address amount amount idx
00: 542d84dd480ce082bbb9a419f7b1d803365b3a294d55dbc0fb213065ef40b465 17.495310331000 884601 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": 466320, "vin": [ { "gen": { "height": 466310 } } ], "vout": [ { "amount": 17495310331, "target": { "key": "542d84dd480ce082bbb9a419f7b1d803365b3a294d55dbc0fb213065ef40b465" } } ], "extra": [ 1, 243, 138, 139, 121, 235, 103, 12, 53, 65, 237, 152, 71, 43, 177, 192, 203, 28, 3, 158, 151, 67, 226, 32, 126, 142, 100, 37, 11, 242, 146, 142, 11, 2, 17, 0, 0, 0, 2, 162, 114, 185, 203, 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