Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d24f296323f59988e8a649a4b9ba968f136138db8d18baf8dcc23f49448525aa

Tx prefix hash: 48ef8da7c9f0923e1387492e32b0f8ed354d7116d2890f3df31069591152517d
Tx public key: d65775a2b10381b86bb7d3fbe85d6eb9e22a7f4cc904258d628ddf2e342a64ae
Timestamp: 1722692761 Timestamp [UCT]: 2024-08-03 13:46:01 Age [y:d:h:m:s]: 00:113:09:33:29
Block: 1079866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81146 RingCT/type: yes/0
Extra: 01d65775a2b10381b86bb7d3fbe85d6eb9e22a7f4cc904258d628ddf2e342a64ae02110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d2a77d86d2dd71cd77d448664c3fd4fda29a7d34d697bb01b1adff57a819caf 0.600000000000 1553007 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": 1079876, "vin": [ { "gen": { "height": 1079866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d2a77d86d2dd71cd77d448664c3fd4fda29a7d34d697bb01b1adff57a819caf" } } ], "extra": [ 1, 214, 87, 117, 162, 177, 3, 129, 184, 107, 183, 211, 251, 232, 93, 110, 185, 226, 42, 127, 76, 201, 4, 37, 141, 98, 141, 223, 46, 52, 42, 100, 174, 2, 17, 0, 0, 0, 15, 233, 20, 221, 21, 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